Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbccc5657ba04736380e207dc0c55af4258dab11a5475d3d790b83dae1ca7e9e

Tx prefix hash: 4575bb1a3e93e9d9c2e7ff6c26ad681c0a1b27d40300b1750c98907d61ae246d
Tx public key: 1dfd5d9cd31fc754addf61caf3989ba0137bdc227e1c379af9b6b8416f6709bf
Timestamp: 1737480927 Timestamp [UCT]: 2025-01-21 17:35:27 Age [y:d:h:m:s]: 00:329:23:06:48
Block: 1202281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233417 RingCT/type: yes/0
Extra: 011dfd5d9cd31fc754addf61caf3989ba0137bdc227e1c379af9b6b8416f6709bf021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d568e0a39efd60ae39f12c58899a86d2023b33944499dcbe8a964b4474550c0 0.600000000000 1688944 of 15

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": 1202291, "vin": [ { "gen": { "height": 1202281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d568e0a39efd60ae39f12c58899a86d2023b33944499dcbe8a964b4474550c0" } } ], "extra": [ 1, 29, 253, 93, 156, 211, 31, 199, 84, 173, 223, 97, 202, 243, 152, 155, 160, 19, 123, 220, 34, 126, 28, 55, 154, 249, 182, 184, 65, 111, 103, 9, 191, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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