Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e4b62b1064a950301d5a5a09e1707fdc465605834c269e31418e9e7219500b1

Tx prefix hash: 5464dc041dd117f70b5a8743123e24eef3d9ea704000ba5036858c546b56063f
Tx public key: e6621e35a354dde9d906cfedbd496833b78e2f61b98375f0baf7ddb041a85795
Timestamp: 1706859263 Timestamp [UCT]: 2024-02-02 07:34:23 Age [y:d:h:m:s]: 01:076:01:30:51
Block: 948606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315431 RingCT/type: yes/0
Extra: 01e6621e35a354dde9d906cfedbd496833b78e2f61b98375f0baf7ddb041a8579502110000000310a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36ed1616b0b4a530e13b6b7fc694f4c2a9fd0b34be0cc881175ad18a7f1e83bb 0.600000000000 1407050 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": 948616, "vin": [ { "gen": { "height": 948606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36ed1616b0b4a530e13b6b7fc694f4c2a9fd0b34be0cc881175ad18a7f1e83bb" } } ], "extra": [ 1, 230, 98, 30, 53, 163, 84, 221, 233, 217, 6, 207, 237, 189, 73, 104, 51, 183, 142, 47, 97, 185, 131, 117, 240, 186, 247, 221, 176, 65, 168, 87, 149, 2, 17, 0, 0, 0, 3, 16, 161, 116, 143, 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