Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5854dfbcf92966a7ee3d77246d595bb271ae46ce0316b5b6796f1390c61d3410

Tx prefix hash: bccbeb174272cf4456af6298e3f1ae3cc02d8fea8f6f881a3e5ae505169a3e93
Tx public key: 43626990105bf0fea825726cca0e1ad37006798ff3efd4d0c9b6e6c197055bf6
Timestamp: 1700274864 Timestamp [UCT]: 2023-11-18 02:34:24 Age [y:d:h:m:s]: 01:141:08:11:51
Block: 894023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362184 RingCT/type: yes/0
Extra: 0143626990105bf0fea825726cca0e1ad37006798ff3efd4d0c9b6e6c197055bf602110000000233af99f4000000000000000000

1 output(s) for total of 0.669469300000 dcy

stealth address amount amount idx
00: 5c2f319a2ddff4d188a5c611acae9ac1aacf07859b5a3a2836937d6241a9000f 0.669469300000 1350210 of 0

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": 894033, "vin": [ { "gen": { "height": 894023 } } ], "vout": [ { "amount": 669469300, "target": { "key": "5c2f319a2ddff4d188a5c611acae9ac1aacf07859b5a3a2836937d6241a9000f" } } ], "extra": [ 1, 67, 98, 105, 144, 16, 91, 240, 254, 168, 37, 114, 108, 202, 14, 26, 211, 112, 6, 121, 143, 243, 239, 212, 208, 201, 182, 230, 193, 151, 5, 91, 246, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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