Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0de5e0072627c15f61313b2b40ca5ff831e1b916dacce12537e2d791bedc06b9

Tx prefix hash: 0d97707d2ba6536f7e14a2c000bdea0fdf4bd9531e9c99e9b4c713640add576c
Tx public key: 50f69ff56f604a80519748d51d02fc1ad24e6776fe58cf10f8dfc6e648361fb9
Timestamp: 1729578767 Timestamp [UCT]: 2024-10-22 06:32:47 Age [y:d:h:m:s]: 00:097:13:10:21
Block: 1136925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69511 RingCT/type: yes/0
Extra: 0150f69ff56f604a80519748d51d02fc1ad24e6776fe58cf10f8dfc6e648361fb9021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e64b99dbf6a9748f11b58504b033d32845cc5fe3ceb505cb59c30b7a3feb303c 0.600000000000 1620322 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": 1136935, "vin": [ { "gen": { "height": 1136925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e64b99dbf6a9748f11b58504b033d32845cc5fe3ceb505cb59c30b7a3feb303c" } } ], "extra": [ 1, 80, 246, 159, 245, 111, 96, 74, 128, 81, 151, 72, 213, 29, 2, 252, 26, 210, 78, 103, 118, 254, 88, 207, 16, 248, 223, 198, 230, 72, 54, 31, 185, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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