Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0b00d083d6604522ece5716fc4b1ab1551f2d2189de641d2dfe9c424c89a115

Tx prefix hash: 5ebb91acace983358682c67d4b5b3ca6fd6b196e1ac882fbf3a7759ac93b9cd1
Tx public key: 8dc7df1248b7db71243a6f556d4a5cf712faf63031dc686bfaf8e93d5a26ddd7
Timestamp: 1712339856 Timestamp [UCT]: 2024-04-05 17:57:36 Age [y:d:h:m:s]: 00:325:11:54:16
Block: 994013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232720 RingCT/type: yes/0
Extra: 018dc7df1248b7db71243a6f556d4a5cf712faf63031dc686bfaf8e93d5a26ddd702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c4d35e273caef946d1e219d39f47a3c9d825ffcefa2d346a6c95b9e6a1f9622 0.600000000000 1454409 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": 994023, "vin": [ { "gen": { "height": 994013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c4d35e273caef946d1e219d39f47a3c9d825ffcefa2d346a6c95b9e6a1f9622" } } ], "extra": [ 1, 141, 199, 223, 18, 72, 183, 219, 113, 36, 58, 111, 85, 109, 74, 92, 247, 18, 250, 246, 48, 49, 220, 104, 107, 250, 248, 233, 61, 90, 38, 221, 215, 2, 17, 0, 0, 0, 1, 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