Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a04dd870e51c4cd75d74a3d0339d1deaafefd9733d9f932acbf1a27320396b2d

Tx prefix hash: bc894ebc9e4c2c221ae9bf42858a9a8ab3726a573fb704152206d86891659230
Tx public key: 31361961a363b2f952ae91cc11188e4f6188f28f371adc6b2b6d12a38137614f
Timestamp: 1729849984 Timestamp [UCT]: 2024-10-25 09:53:04 Age [y:d:h:m:s]: 00:148:15:32:02
Block: 1139183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106034 RingCT/type: yes/0
Extra: 0131361961a363b2f952ae91cc11188e4f6188f28f371adc6b2b6d12a38137614f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f1764cc4ea1bcbbfb16548f8214fda9827e3b94a47950b644328f0397c2ae04 0.600000000000 1622954 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": 1139193, "vin": [ { "gen": { "height": 1139183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f1764cc4ea1bcbbfb16548f8214fda9827e3b94a47950b644328f0397c2ae04" } } ], "extra": [ 1, 49, 54, 25, 97, 163, 99, 178, 249, 82, 174, 145, 204, 17, 24, 142, 79, 97, 136, 242, 143, 55, 26, 220, 107, 43, 109, 18, 163, 129, 55, 97, 79, 2, 17, 0, 0, 0, 1, 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