Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3032787e0cb0ca95478bc42b80c794c45c0eb6416a3eec3ca6fa64961a22205b

Tx prefix hash: e6636e82594c2e512bd975376fc2e974c02e339fff05cec032c0a3f600f6d9ec
Tx public key: bfdeb92153131e674e0299cb32243a81dc7e42e68f3bb8f66485d473b60f0f15
Timestamp: 1749204133 Timestamp [UCT]: 2025-06-06 10:02:13 Age [y:d:h:m:s]: 00:167:21:44:29
Block: 1299125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117675 RingCT/type: yes/0
Extra: 01bfdeb92153131e674e0299cb32243a81dc7e42e68f3bb8f66485d473b60f0f1502110000000e43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dc434e3188dc801613d0011272f0aa8c8c47e5555a24a81f7fe077e254968c3 0.600000000000 1786660 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": 1299135, "vin": [ { "gen": { "height": 1299125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dc434e3188dc801613d0011272f0aa8c8c47e5555a24a81f7fe077e254968c3" } } ], "extra": [ 1, 191, 222, 185, 33, 83, 19, 30, 103, 78, 2, 153, 203, 50, 36, 58, 129, 220, 126, 66, 230, 143, 59, 184, 246, 100, 133, 212, 115, 182, 15, 15, 21, 2, 17, 0, 0, 0, 14, 67, 132, 109, 102, 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