Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b96460a10eae76c314d9b841d92a1638251d3afafa23deceab24d26af60fc4b5

Tx prefix hash: 663847ce75b226dd59d7db894a7a8bd2e283b588d960df5b4eb21d226322cba4
Tx public key: e8338a9007122d6a9ad788fdd86715370d02fbf58eb87f5a9c76ad63e81781c6
Timestamp: 1715822975 Timestamp [UCT]: 2024-05-16 01:29:35 Age [y:d:h:m:s]: 00:285:05:39:25
Block: 1022932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203838 RingCT/type: yes/0
Extra: 01e8338a9007122d6a9ad788fdd86715370d02fbf58eb87f5a9c76ad63e81781c602110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cb81e16f1ff6c8d95c0c02d9d416caf80158e8fae888b64f26d7d72c20c5d18 0.600000000000 1487677 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": 1022942, "vin": [ { "gen": { "height": 1022932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cb81e16f1ff6c8d95c0c02d9d416caf80158e8fae888b64f26d7d72c20c5d18" } } ], "extra": [ 1, 232, 51, 138, 144, 7, 18, 45, 106, 154, 215, 136, 253, 216, 103, 21, 55, 13, 2, 251, 245, 142, 184, 127, 90, 156, 118, 173, 99, 232, 23, 129, 198, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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