Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1169b678e2d1b545e2cb5f95fa0d86f59394a2feeb6877ae2950a2b6b5951d9a

Tx prefix hash: 3a72678c1a46b284f8958147c3b715961fa425eb399dd84b5278108800db8687
Tx public key: 33ea7c51c3967a6a5ba872245ea9f8100bfa3797e71955c423d15659fc898218
Timestamp: 1741607165 Timestamp [UCT]: 2025-03-10 11:46:05 Age [y:d:h:m:s]: 00:256:11:26:10
Block: 1236237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181030 RingCT/type: yes/0
Extra: 0133ea7c51c3967a6a5ba872245ea9f8100bfa3797e71955c423d15659fc898218021100000016007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82376ccbdfc3b246b43b2007404a42eec2aa29e3daf60dcff39d0e71b39a0a1f 0.600000000000 1723182 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": 1236247, "vin": [ { "gen": { "height": 1236237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82376ccbdfc3b246b43b2007404a42eec2aa29e3daf60dcff39d0e71b39a0a1f" } } ], "extra": [ 1, 51, 234, 124, 81, 195, 150, 122, 106, 91, 168, 114, 36, 94, 169, 248, 16, 11, 250, 55, 151, 231, 25, 85, 196, 35, 209, 86, 89, 252, 137, 130, 24, 2, 17, 0, 0, 0, 22, 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