Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d61cf04de38c151d6df80f49a52fbfd0e8ae0bbdddaaee64fd669e73409675d6

Tx prefix hash: 683da6eb117c7eeafdfefc8984dc10a251d44cc45f104030328ef7d7214e86e4
Tx public key: ba4b9e97f08d35fd3daa6ab5133efde8ccdd5790adfe8ba71950b916c2120a6b
Timestamp: 1732268301 Timestamp [UCT]: 2024-11-22 09:38:21 Age [y:d:h:m:s]: 00:001:20:15:06
Block: 1159161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1325 RingCT/type: yes/0
Extra: 01ba4b9e97f08d35fd3daa6ab5133efde8ccdd5790adfe8ba71950b916c2120a6b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96c2813d52b5e5bc83442d70f29b07a1d2746e59e5bbe99020c52a53a9665ec3 0.600000000000 1644794 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": 1159171, "vin": [ { "gen": { "height": 1159161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96c2813d52b5e5bc83442d70f29b07a1d2746e59e5bbe99020c52a53a9665ec3" } } ], "extra": [ 1, 186, 75, 158, 151, 240, 141, 53, 253, 61, 170, 106, 181, 19, 62, 253, 232, 204, 221, 87, 144, 173, 254, 139, 167, 25, 80, 185, 22, 194, 18, 10, 107, 2, 17, 0, 0, 0, 3, 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