Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6308a43b2e122b765b117ef06e81b13cdb900e4daf47251d61360cea2cbacd8d

Tx prefix hash: a53dd4333a5fd5dc35f0ac910c7f357032756ec8668dd8ff1f3f408013cc664b
Tx public key: 7727e5fecf8e9462d7a7ee4ec1f1dc81a3679e789a2cb9317d01f2c8f8ca4a8e
Timestamp: 1709555283 Timestamp [UCT]: 2024-03-04 12:28:03 Age [y:d:h:m:s]: 00:310:18:02:07
Block: 970966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222451 RingCT/type: yes/0
Extra: 017727e5fecf8e9462d7a7ee4ec1f1dc81a3679e789a2cb9317d01f2c8f8ca4a8e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31c79f92a9ed9b6cd9ffdcfebed0832f3df3c5c2eaf01f14eafac5039abf11ae 0.600000000000 1430839 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": 970976, "vin": [ { "gen": { "height": 970966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31c79f92a9ed9b6cd9ffdcfebed0832f3df3c5c2eaf01f14eafac5039abf11ae" } } ], "extra": [ 1, 119, 39, 229, 254, 207, 142, 148, 98, 215, 167, 238, 78, 193, 241, 220, 129, 163, 103, 158, 120, 154, 44, 185, 49, 125, 1, 242, 200, 248, 202, 74, 142, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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