Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c8bbf5c45401d8be5f4a90604b04c110e5c52e41211bbf0e61288d9a13be688

Tx prefix hash: 0b2739f681f717f2751702e9546b120d49c36ee64d7c0bc978080e06985f2575
Tx public key: 0a300032befdf18d191efc625dbb976bcfdefa9ae6ff46a3860bfade64462d7f
Timestamp: 1711263331 Timestamp [UCT]: 2024-03-24 06:55:31 Age [y:d:h:m:s]: 01:226:23:53:15
Block: 985147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420883 RingCT/type: yes/0
Extra: 010a300032befdf18d191efc625dbb976bcfdefa9ae6ff46a3860bfade64462d7f02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7d96375d40d3449be7dd9cff2b002bf7a541f5e5eaaffbd116452336bb92d4d 0.600000000000 1445354 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": 985157, "vin": [ { "gen": { "height": 985147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7d96375d40d3449be7dd9cff2b002bf7a541f5e5eaaffbd116452336bb92d4d" } } ], "extra": [ 1, 10, 48, 0, 50, 190, 253, 241, 141, 25, 30, 252, 98, 93, 187, 151, 107, 207, 222, 250, 154, 230, 255, 70, 163, 134, 11, 250, 222, 100, 70, 45, 127, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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