Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 532239db42a15978b75a21d307e10d9ae72bba2909ce691b473598c75f4606e9

Tx prefix hash: 6588be13492e82c27b6a27273d7d4aade5cd41915ac4152e3be887bb576eabb7
Tx public key: b5d4ad812b6d57f627af117ecfa2288da4c68376d17041aa4a136b5734a33c21
Timestamp: 1705539363 Timestamp [UCT]: 2024-01-18 00:56:03 Age [y:d:h:m:s]: 01:116:15:07:09
Block: 937646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344483 RingCT/type: yes/0
Extra: 01b5d4ad812b6d57f627af117ecfa2288da4c68376d17041aa4a136b5734a33c2102110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a34cff1b59fff1c8e8d69d2fe3d19ff789ab4abf3717cec1d6f9668c094f031e 0.600000000000 1395708 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": 937656, "vin": [ { "gen": { "height": 937646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a34cff1b59fff1c8e8d69d2fe3d19ff789ab4abf3717cec1d6f9668c094f031e" } } ], "extra": [ 1, 181, 212, 173, 129, 43, 109, 87, 246, 39, 175, 17, 126, 207, 162, 40, 141, 164, 198, 131, 118, 209, 112, 65, 170, 74, 19, 107, 87, 52, 163, 60, 33, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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