Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86e08fd29f4a2a38e0d224dee79c42c4e94ba8d7de0a2fe3bb185c1e5c195fff

Tx prefix hash: b049feae87740ede6d4eb8d63760efcb532eb75356a3bb0126a8ea99a68d188b
Tx public key: 6af4cfa7239fefa08fbbb6f7cfbb52ad980c8f08f9a435b73b1fad30901faa48
Timestamp: 1735577584 Timestamp [UCT]: 2024-12-30 16:53:04 Age [y:d:h:m:s]: 00:076:19:40:25
Block: 1186562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54709 RingCT/type: yes/0
Extra: 016af4cfa7239fefa08fbbb6f7cfbb52ad980c8f08f9a435b73b1fad30901faa48021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d1f625c998c482981f6f7791faf84fb69a30a8459d36652bb26aaab1f74404a 0.600000000000 1673045 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": 1186572, "vin": [ { "gen": { "height": 1186562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d1f625c998c482981f6f7791faf84fb69a30a8459d36652bb26aaab1f74404a" } } ], "extra": [ 1, 106, 244, 207, 167, 35, 159, 239, 160, 143, 187, 182, 247, 207, 187, 82, 173, 152, 12, 143, 8, 249, 164, 53, 183, 59, 31, 173, 48, 144, 31, 170, 72, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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