Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e7fd68330d2749220c16532a50a7db901cdb7688fd568f6719e4ec43b68541c

Tx prefix hash: bbcfcef3b1ab207627436f2cb48eb418fe5f2ab3728ca4bf4b7aa68f80fe9f1e
Tx public key: 6ace11efe1ab9f61281179d1688d8064bde48f7944d4e67f2cbd6cd75e3e2fc6
Timestamp: 1735287935 Timestamp [UCT]: 2024-12-27 08:25:35 Age [y:d:h:m:s]: 00:170:03:38:48
Block: 1184167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121349 RingCT/type: yes/0
Extra: 016ace11efe1ab9f61281179d1688d8064bde48f7944d4e67f2cbd6cd75e3e2fc60211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9775b12296f2af45c997823361d7d3dcf81b76b070e0cf7bb240d4d765226b82 0.600000000000 1670622 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": 1184177, "vin": [ { "gen": { "height": 1184167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9775b12296f2af45c997823361d7d3dcf81b76b070e0cf7bb240d4d765226b82" } } ], "extra": [ 1, 106, 206, 17, 239, 225, 171, 159, 97, 40, 17, 121, 209, 104, 141, 128, 100, 189, 228, 143, 121, 68, 212, 230, 127, 44, 189, 108, 215, 94, 62, 47, 198, 2, 17, 0, 0, 0, 5, 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