Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f53dbc4b26da0e6dc4f62abd0198dfe39b4db8b795c454e0c56f05dcfd0c405b

Tx prefix hash: 15c1bce97f79e2878639ddc698d03b6516138e5bf2efb0c26d83479a66059b69
Tx public key: 52b4a5c585966eec89c5402af26d98ec17d85fe9e75f5291773edaaa73be4724
Timestamp: 1726352210 Timestamp [UCT]: 2024-09-14 22:16:50 Age [y:d:h:m:s]: 00:214:10:22:50
Block: 1110222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153078 RingCT/type: yes/0
Extra: 0152b4a5c585966eec89c5402af26d98ec17d85fe9e75f5291773edaaa73be4724021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e665fec6c999dbe74f0f1db0aea1a4a11c6a819ad0562a2e19cc98bdecd84a5e 0.600000000000 1588747 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": 1110232, "vin": [ { "gen": { "height": 1110222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e665fec6c999dbe74f0f1db0aea1a4a11c6a819ad0562a2e19cc98bdecd84a5e" } } ], "extra": [ 1, 82, 180, 165, 197, 133, 150, 110, 236, 137, 197, 64, 42, 242, 109, 152, 236, 23, 216, 95, 233, 231, 95, 82, 145, 119, 62, 218, 170, 115, 190, 71, 36, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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