Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1be597eeb974fa60bffd24bdb99957a3a38ef695d321a19f71264d7ae1aa9cb

Tx prefix hash: d1f3765c4dd04ad9cecd314f6d53e67e8c2bd46496b14b6ab15e8f2aefdda789
Tx public key: 79379da287266f3b51b1cc012dae407a5d14cdb784819872bfa5f1e763fc707a
Timestamp: 1736671469 Timestamp [UCT]: 2025-01-12 08:44:29 Age [y:d:h:m:s]: 00:065:02:29:18
Block: 1195630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46317 RingCT/type: yes/0
Extra: 0179379da287266f3b51b1cc012dae407a5d14cdb784819872bfa5f1e763fc707a0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8c136a5f366e6689f0bdf7592913a6a774a20cdef544360ec89f0b07ccda620 0.600000000000 1682221 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": 1195640, "vin": [ { "gen": { "height": 1195630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8c136a5f366e6689f0bdf7592913a6a774a20cdef544360ec89f0b07ccda620" } } ], "extra": [ 1, 121, 55, 157, 162, 135, 38, 111, 59, 81, 177, 204, 1, 45, 174, 64, 122, 93, 20, 205, 183, 132, 129, 152, 114, 191, 165, 241, 231, 99, 252, 112, 122, 2, 17, 0, 0, 0, 6, 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