Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71bd9a494406133ab62467d7ee07f59cdf080fd1d7f995bd42a757b726413751

Tx prefix hash: b81f8ec9d8bfaa2765255b9cd09a465bd49276221e1332b4ec1d66dd12f4fb50
Tx public key: ff0d4bd7c4da8ae37d2be1a8aa7ede4bfec33c2b6efdd01f05767fa8837b617e
Timestamp: 1728053032 Timestamp [UCT]: 2024-10-04 14:43:52 Age [y:d:h:m:s]: 00:203:17:28:04
Block: 1124324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145409 RingCT/type: yes/0
Extra: 01ff0d4bd7c4da8ae37d2be1a8aa7ede4bfec33c2b6efdd01f05767fa8837b617e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32a125305e4ee0fae6edd2a1453a0012ca1b1b8a97c29617d9df040f566da3a9 0.600000000000 1606941 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": 1124334, "vin": [ { "gen": { "height": 1124324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32a125305e4ee0fae6edd2a1453a0012ca1b1b8a97c29617d9df040f566da3a9" } } ], "extra": [ 1, 255, 13, 75, 215, 196, 218, 138, 227, 125, 43, 225, 168, 170, 126, 222, 75, 254, 195, 60, 43, 110, 253, 208, 31, 5, 118, 127, 168, 131, 123, 97, 126, 2, 17, 0, 0, 0, 2, 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