Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 287c9906f42d5946c1adad71e17fcb9e0f7cb18cbca36b2f1635b108e1f09dc9

Tx prefix hash: b72b4ea4ef7ec9949a752ffed94d9d88af1cba7b2b2d3cefad4676aed7278f3b
Tx public key: f223409f38cf1c0d9b8fb30af77e76673357d034d40df5bc80363a818014d2ee
Timestamp: 1722306122 Timestamp [UCT]: 2024-07-30 02:22:02 Age [y:d:h:m:s]: 01:180:02:15:24
Block: 1076671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387127 RingCT/type: yes/0
Extra: 01f223409f38cf1c0d9b8fb30af77e76673357d034d40df5bc80363a818014d2ee021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68b427efc1bc2ede1b1b9ab48f11b6a79c111dd70a9b3bc517a7b8e5db290833 0.600000000000 1549212 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": 1076681, "vin": [ { "gen": { "height": 1076671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68b427efc1bc2ede1b1b9ab48f11b6a79c111dd70a9b3bc517a7b8e5db290833" } } ], "extra": [ 1, 242, 35, 64, 159, 56, 207, 28, 13, 155, 143, 179, 10, 247, 126, 118, 103, 51, 87, 208, 52, 212, 13, 245, 188, 128, 54, 58, 129, 128, 20, 210, 238, 2, 17, 0, 0, 0, 7, 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