Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70c165ddda2b7d4b2fa761f67036bf123a477b2402e2fb66a5f2b5dd7467d3a6

Tx prefix hash: 1e92c22c867ffa7de40369229b840b1e58a43dcfd7167c985ba3ef2d356af6b4
Tx public key: 5381d3fe79090d4b29d09e5accb6f1887f652204d9538abf7973023754fd0467
Timestamp: 1712863572 Timestamp [UCT]: 2024-04-11 19:26:12 Age [y:d:h:m:s]: 01:042:14:23:21
Block: 998369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291452 RingCT/type: yes/0
Extra: 015381d3fe79090d4b29d09e5accb6f1887f652204d9538abf7973023754fd04670211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51355ff8d8ebf1efbbdc332d7997e98fb1ba2b7d65c50daa6e6944cc3694b175 0.600000000000 1458815 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": 998379, "vin": [ { "gen": { "height": 998369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51355ff8d8ebf1efbbdc332d7997e98fb1ba2b7d65c50daa6e6944cc3694b175" } } ], "extra": [ 1, 83, 129, 211, 254, 121, 9, 13, 75, 41, 208, 158, 90, 204, 182, 241, 136, 127, 101, 34, 4, 217, 83, 138, 191, 121, 115, 2, 55, 84, 253, 4, 103, 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