Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 594c0864b8e45680293040cc9afe64cc94a0b0fba2353ba25b63d6dc1a06127c

Tx prefix hash: a8339c843135bc6d2b122151a809ef0339de725d853f43d60d6cd702f1337d0f
Tx public key: c3639f26a181f9e0e976b50b00b3db96b2c80cb36748d5810555f9403965a3b3
Timestamp: 1717659250 Timestamp [UCT]: 2024-06-06 07:34:10 Age [y:d:h:m:s]: 00:232:20:48:42
Block: 1038155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166600 RingCT/type: yes/0
Extra: 01c3639f26a181f9e0e976b50b00b3db96b2c80cb36748d5810555f9403965a3b30211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3dbe96797fc65f8896145065b6b12980c090e73c8c2993f777f1467c22c016d 0.600000000000 1506716 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": 1038165, "vin": [ { "gen": { "height": 1038155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3dbe96797fc65f8896145065b6b12980c090e73c8c2993f777f1467c22c016d" } } ], "extra": [ 1, 195, 99, 159, 38, 161, 129, 249, 224, 233, 118, 181, 11, 0, 179, 219, 150, 178, 200, 12, 179, 103, 72, 213, 129, 5, 85, 249, 64, 57, 101, 163, 179, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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