Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59bc84f745f091f7226cb95a6cd6d71876f38a40598134fee7e1fe501b56158f

Tx prefix hash: 59562ecf78ff423d7961f276dad3a6a6385fa1c611e60dddc7128bea2a8710b4
Tx public key: 111c3fc5d8fff52018f8f477641dd88c46ba1d1bcf58597541b7aa4eaf1ae234
Timestamp: 1707932272 Timestamp [UCT]: 2024-02-14 17:37:52 Age [y:d:h:m:s]: 00:335:06:15:19
Block: 957497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240005 RingCT/type: yes/0
Extra: 01111c3fc5d8fff52018f8f477641dd88c46ba1d1bcf58597541b7aa4eaf1ae23402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8f9a52cf4237a03344f8f10297044c3704d52e128647a0ca7fc1ca20b4b1013 0.600000000000 1416815 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": 957507, "vin": [ { "gen": { "height": 957497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8f9a52cf4237a03344f8f10297044c3704d52e128647a0ca7fc1ca20b4b1013" } } ], "extra": [ 1, 17, 28, 63, 197, 216, 255, 245, 32, 24, 248, 244, 119, 100, 29, 216, 140, 70, 186, 29, 27, 207, 88, 89, 117, 65, 183, 170, 78, 175, 26, 226, 52, 2, 17, 0, 0, 0, 4, 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