Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2c1c4a051977b2a3eb471380506174f677d77bdba41134c8b0daf0027b4b322

Tx prefix hash: 5f7e9ca7bb39518a1d2abf3ffc49e5972230a3bbafe5c044c348619af4277333
Tx public key: 59825b8da4a8ab0d85ef5dc2773b640959da4e897cc44ff3bad21fadb56a9dda
Timestamp: 1761177794 Timestamp [UCT]: 2025-10-23 00:03:14 Age [y:d:h:m:s]: 00:101:12:10:10
Block: 1395826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72487 RingCT/type: yes/0
Extra: 0159825b8da4a8ab0d85ef5dc2773b640959da4e897cc44ff3bad21fadb56a9dda021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a34ee56fdc8730e08ef593cf539a9c5a2d882f4ae3e5debd3d01653b624f7a8 0.600000000000 1884109 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": 1395836, "vin": [ { "gen": { "height": 1395826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a34ee56fdc8730e08ef593cf539a9c5a2d882f4ae3e5debd3d01653b624f7a8" } } ], "extra": [ 1, 89, 130, 91, 141, 164, 168, 171, 13, 133, 239, 93, 194, 119, 59, 100, 9, 89, 218, 78, 137, 124, 196, 79, 243, 186, 210, 31, 173, 181, 106, 157, 218, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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