Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b567ea249bf12398e83af873942e52cab8dbe7591366fecb37ac34c2011dcd3

Tx prefix hash: 187864a73875085f0c0fcd9e93bd512719a8caa483a42c1f14629b67c200815a
Tx public key: 1286a0d7b1cd3fa87d1636a049a5d508396998d2c84ba4b27b964cd08ec68b5d
Timestamp: 1710284518 Timestamp [UCT]: 2024-03-12 23:01:58 Age [y:d:h:m:s]: 01:267:06:00:25
Block: 977022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449743 RingCT/type: yes/0
Extra: 011286a0d7b1cd3fa87d1636a049a5d508396998d2c84ba4b27b964cd08ec68b5d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb947553fb70bdc97e37b06f420951c74dfc3690f77c2d59ea693e62e9cb7512 0.600000000000 1437023 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": 977032, "vin": [ { "gen": { "height": 977022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb947553fb70bdc97e37b06f420951c74dfc3690f77c2d59ea693e62e9cb7512" } } ], "extra": [ 1, 18, 134, 160, 215, 177, 205, 63, 168, 125, 22, 54, 160, 73, 165, 213, 8, 57, 105, 152, 210, 200, 75, 164, 178, 123, 150, 76, 208, 142, 198, 139, 93, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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