Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6586ca31bf1278e7b71fb40ba86a885ba8b087b2c3271d219c4864a73b4c4fe0

Tx prefix hash: 347745d2058299110185a930a324d9d790df0c5cc64d77bb4489b2c5bfb4acec
Tx public key: 194e7e27d749247611aeb150f9244ffdfa76bedbea8d54aaf3ae938c5de55ccf
Timestamp: 1732573616 Timestamp [UCT]: 2024-11-25 22:26:56 Age [y:d:h:m:s]: 00:155:03:16:47
Block: 1161694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110717 RingCT/type: yes/0
Extra: 01194e7e27d749247611aeb150f9244ffdfa76bedbea8d54aaf3ae938c5de55ccf0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06fa315085ae5cd7e6d95acf37ada7fbc8905eb2951f03a29d871579fe482c4c 0.600000000000 1647349 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": 1161704, "vin": [ { "gen": { "height": 1161694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06fa315085ae5cd7e6d95acf37ada7fbc8905eb2951f03a29d871579fe482c4c" } } ], "extra": [ 1, 25, 78, 126, 39, 215, 73, 36, 118, 17, 174, 177, 80, 249, 36, 79, 253, 250, 118, 190, 219, 234, 141, 84, 170, 243, 174, 147, 140, 93, 229, 92, 207, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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