Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7c3acc0af9b67feb03dd1e60aec956864d8187ff67cae3a5c5c94278fc052a6

Tx prefix hash: d900e99ee37c35179fcff56502da1bdb8f34729a37ffede0ffee5b4b2b0240ae
Tx public key: 51fc09d114f9f86a94c277fad81ea6fb2fee804992d02c890607afee2917d70a
Timestamp: 1711313680 Timestamp [UCT]: 2024-03-24 20:54:40 Age [y:d:h:m:s]: 01:083:17:14:09
Block: 985565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320716 RingCT/type: yes/0
Extra: 0151fc09d114f9f86a94c277fad81ea6fb2fee804992d02c890607afee2917d70a0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac86cebea68d1280ec5f2d34bd0368f8a5ad9ff64b5561ed7f5bf8f6bcad61cd 0.600000000000 1445780 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": 985575, "vin": [ { "gen": { "height": 985565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac86cebea68d1280ec5f2d34bd0368f8a5ad9ff64b5561ed7f5bf8f6bcad61cd" } } ], "extra": [ 1, 81, 252, 9, 209, 20, 249, 248, 106, 148, 194, 119, 250, 216, 30, 166, 251, 47, 238, 128, 73, 146, 208, 44, 137, 6, 7, 175, 238, 41, 23, 215, 10, 2, 17, 0, 0, 0, 4, 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