Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4640a05a20243efd23172709ff4f7bd1e576311ec1771fde4bb46ce1e024579f

Tx prefix hash: f5a2f2f9573e669b6e307a9f5d4e47d991c3a4d1bee5724a16725e3bb21735be
Tx public key: 7effb2b61a38d460f7ad5227e4a33f5cc22cd280e306f86ad7692a6de7f4766c
Timestamp: 1719704306 Timestamp [UCT]: 2024-06-29 23:38:26 Age [y:d:h:m:s]: 00:258:15:16:57
Block: 1055096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184820 RingCT/type: yes/0
Extra: 017effb2b61a38d460f7ad5227e4a33f5cc22cd280e306f86ad7692a6de7f4766c02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4f078f4c99cefd573c2a8f63061a8296402ad6212ad392fc852eb657e22cc70 0.600000000000 1525489 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": 1055106, "vin": [ { "gen": { "height": 1055096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4f078f4c99cefd573c2a8f63061a8296402ad6212ad392fc852eb657e22cc70" } } ], "extra": [ 1, 126, 255, 178, 182, 26, 56, 212, 96, 247, 173, 82, 39, 228, 163, 63, 92, 194, 44, 210, 128, 227, 6, 248, 106, 215, 105, 42, 109, 231, 244, 118, 108, 2, 17, 0, 0, 0, 7, 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