Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 244ee49ce3b2cd2631535e24e7f9da29ab529282e05f75d608c0ba81e6439b72

Tx prefix hash: 0aeaeb924c8db8916b43216a41db860933b0df3a361920a63d78883786229eb8
Tx public key: 652ffb87812ee2ccdf0c8f1ab780e1377e8c1c3e7c040457aa8561eb440e9d02
Timestamp: 1736256641 Timestamp [UCT]: 2025-01-07 13:30:41 Age [y:d:h:m:s]: 00:093:18:03:12
Block: 1192197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66792 RingCT/type: yes/0
Extra: 01652ffb87812ee2ccdf0c8f1ab780e1377e8c1c3e7c040457aa8561eb440e9d020211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9c511b2d652f5c227ccfca947adc936ddd092c1ca75150d7adb5dd4ec4867e5 0.600000000000 1678746 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": 1192207, "vin": [ { "gen": { "height": 1192197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9c511b2d652f5c227ccfca947adc936ddd092c1ca75150d7adb5dd4ec4867e5" } } ], "extra": [ 1, 101, 47, 251, 135, 129, 46, 226, 204, 223, 12, 143, 26, 183, 128, 225, 55, 126, 140, 28, 62, 124, 4, 4, 87, 170, 133, 97, 235, 68, 14, 157, 2, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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