Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b727ee921b5354f94ea248d0632a53505d4727d3c569ffbc36b3a139d3d7d66

Tx prefix hash: db0e8ac8ec95dbbc0623eba7514eba70893e13d0915e3897f96904133627956f
Tx public key: 27f886bf353339a3fa88e2bc3140b9a1ad98f410e0c2765e5e4dc49bd1e38678
Timestamp: 1726990191 Timestamp [UCT]: 2024-09-22 07:29:51 Age [y:d:h:m:s]: 00:173:08:19:57
Block: 1115510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123716 RingCT/type: yes/0
Extra: 0127f886bf353339a3fa88e2bc3140b9a1ad98f410e0c2765e5e4dc49bd1e38678021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bee8fc7c6433c1e9a50a9ddbc78f643b29e79a49b0b1b66063efae58ef91a58 0.600000000000 1595667 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": 1115520, "vin": [ { "gen": { "height": 1115510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bee8fc7c6433c1e9a50a9ddbc78f643b29e79a49b0b1b66063efae58ef91a58" } } ], "extra": [ 1, 39, 248, 134, 191, 53, 51, 57, 163, 250, 136, 226, 188, 49, 64, 185, 161, 173, 152, 244, 16, 224, 194, 118, 94, 94, 77, 196, 155, 209, 227, 134, 120, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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