Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81bccc2ddece5388e9f1f255bfe72b6ce470bfbabe8ddde51e7a7d44688aa5f1

Tx prefix hash: 73a96cd689b6833cff693e8e01305451cbf3ac88d4ded3901348d69e91536e22
Tx public key: 8409724e0e87dd184b8fbea93bf29ff6209d23e14e8fa94e023b0e706e94abc4
Timestamp: 1721113384 Timestamp [UCT]: 2024-07-16 07:03:04 Age [y:d:h:m:s]: 01:114:10:40:55
Block: 1066798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340292 RingCT/type: yes/0
Extra: 018409724e0e87dd184b8fbea93bf29ff6209d23e14e8fa94e023b0e706e94abc4021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2718a6245c89effb5ad6849332b83c982df540f0ca05bb735ba08b32c69128da 0.600000000000 1537465 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": 1066808, "vin": [ { "gen": { "height": 1066798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2718a6245c89effb5ad6849332b83c982df540f0ca05bb735ba08b32c69128da" } } ], "extra": [ 1, 132, 9, 114, 78, 14, 135, 221, 24, 75, 143, 190, 169, 59, 242, 159, 246, 32, 157, 35, 225, 78, 143, 169, 78, 2, 59, 14, 112, 110, 148, 171, 196, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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