Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cee2f0494cf5ef1a914d52d91735931b8ad7f9440bdae28fe052ef39f553321b

Tx prefix hash: 50cfb6c56b560d9f0b36f45dc2192fb607a8fa59ef3048a118deeb4359c3724d
Tx public key: da002710b9de848b11ab04bd6bae23aa3d4db7e75c06ca2a0e2f6c759c888f18
Timestamp: 1744785459 Timestamp [UCT]: 2025-04-16 06:37:39 Age [y:d:h:m:s]: 00:022:17:04:03
Block: 1262532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16240 RingCT/type: yes/0
Extra: 01da002710b9de848b11ab04bd6bae23aa3d4db7e75c06ca2a0e2f6c759c888f180211000000076c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 792a8de350ef975d8e6784f7576d25ed6ce04741e4622dc13559217423b3c998 0.600000000000 1749711 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": 1262542, "vin": [ { "gen": { "height": 1262532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "792a8de350ef975d8e6784f7576d25ed6ce04741e4622dc13559217423b3c998" } } ], "extra": [ 1, 218, 0, 39, 16, 185, 222, 132, 139, 17, 171, 4, 189, 107, 174, 35, 170, 61, 77, 183, 231, 92, 6, 202, 42, 14, 47, 108, 117, 156, 136, 143, 24, 2, 17, 0, 0, 0, 7, 108, 152, 170, 61, 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