Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 703487ca5c197fae1dc7cc70e7ecbe89a9b2dbd02b6518ee75d2a4cc627c345a

Tx prefix hash: f2e847422759633fbb647d5711e511bb0841f06ebae6f2769688be9ec39db119
Tx public key: 6fbdb6b67adbe7394bf58c9189fd4e51f54b390d16ddae36a2fb2d07647d207f
Timestamp: 1744242191 Timestamp [UCT]: 2025-04-09 23:43:11 Age [y:d:h:m:s]: 00:034:23:01:23
Block: 1258031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25019 RingCT/type: yes/0
Extra: 016fbdb6b67adbe7394bf58c9189fd4e51f54b390d16ddae36a2fb2d07647d207f0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21032bd71294a25c969a839f7626e05c34ec021a512f41261ae5a23213c9f35e 0.600000000000 1745162 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": 1258041, "vin": [ { "gen": { "height": 1258031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21032bd71294a25c969a839f7626e05c34ec021a512f41261ae5a23213c9f35e" } } ], "extra": [ 1, 111, 189, 182, 182, 122, 219, 231, 57, 75, 245, 140, 145, 137, 253, 78, 81, 245, 75, 57, 13, 22, 221, 174, 54, 162, 251, 45, 7, 100, 125, 32, 127, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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