Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0d6ace20327df900b3046321b2e816e04389834c8959d19fd65b4ee516208953

Tx prefix hash: 3af22acc8be8ea7ae8651273863083ca75199001f8f5711c5f986757c423c653
Tx public key: b74377d5e8d5371a5a3a5a3396843cae4fe1cf112a5ab84c540b5ac1a1c230cd
Timestamp: 1696889124 Timestamp [UCT]: 2023-10-09 22:05:24 Age [y:d:h:m:s]: 01:140:02:07:40
Block: 866160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361120 RingCT/type: yes/0
Extra: 01b74377d5e8d5371a5a3a5a3396843cae4fe1cf112a5ab84c540b5ac1a1c230cd02110000001075e3f0e9000000000000000000

1 output(s) for total of 0.828042052000 dcy

stealth address amount amount idx
00: dfcd4f78ffecc235fa87bb821d190e47081047327b91282a5980294c9d71c094 0.828042052000 1320732 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 866170, "vin": [ { "gen": { "height": 866160 } } ], "vout": [ { "amount": 828042052, "target": { "key": "dfcd4f78ffecc235fa87bb821d190e47081047327b91282a5980294c9d71c094" } } ], "extra": [ 1, 183, 67, 119, 213, 232, 213, 55, 26, 90, 58, 90, 51, 150, 132, 60, 174, 79, 225, 207, 17, 42, 90, 184, 76, 84, 11, 90, 193, 161, 194, 48, 205, 2, 17, 0, 0, 0, 16, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8