Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 355fb10e1389d28cba31456e3f387e72f4250004c4cc7aaf1203e0121037c602

Tx prefix hash: df216d0bdd11358f2d982012fec270dd6a5930a4ddb7346149ee6b8a7059e088
Tx public key: 6ac881b89f5786d68f32d246fca6380a6ee7dcc0d566697e523ff25c2d7c356f
Timestamp: 1718149786 Timestamp [UCT]: 2024-06-11 23:49:46 Age [y:d:h:m:s]: 00:310:18:54:32
Block: 1042223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222106 RingCT/type: yes/0
Extra: 016ac881b89f5786d68f32d246fca6380a6ee7dcc0d566697e523ff25c2d7c356f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e66afc6501ae4f22d62d8e1afbec526a3796cb957b2b153090d2cff70c910ecc 0.600000000000 1511092 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": 1042233, "vin": [ { "gen": { "height": 1042223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e66afc6501ae4f22d62d8e1afbec526a3796cb957b2b153090d2cff70c910ecc" } } ], "extra": [ 1, 106, 200, 129, 184, 159, 87, 134, 214, 143, 50, 210, 70, 252, 166, 56, 10, 110, 231, 220, 192, 213, 102, 105, 126, 82, 63, 242, 92, 45, 124, 53, 111, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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