Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7b1619964970831b29673263ba08f2bd9ff1f69e5c9cf8ae9759adee8631ef7

Tx prefix hash: 34da2e793c6982e0cf83e3bd304dcdb9e81a230dc11b00dfff3d4e12dd149df9
Tx public key: 0c9319ec97a1d12945007e857e1cc1c76bad7ddc8cbb04ec6665a2c0aab64a62
Timestamp: 1734072254 Timestamp [UCT]: 2024-12-13 06:44:14 Age [y:d:h:m:s]: 00:096:04:55:53
Block: 1174134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68542 RingCT/type: yes/0
Extra: 010c9319ec97a1d12945007e857e1cc1c76bad7ddc8cbb04ec6665a2c0aab64a620211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c87baa996f79f490fbb7decab70b72c8d5c3bee6effaa213a5720a4ffced2bb 0.600000000000 1660247 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": 1174144, "vin": [ { "gen": { "height": 1174134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c87baa996f79f490fbb7decab70b72c8d5c3bee6effaa213a5720a4ffced2bb" } } ], "extra": [ 1, 12, 147, 25, 236, 151, 161, 209, 41, 69, 0, 126, 133, 126, 28, 193, 199, 107, 173, 125, 220, 140, 187, 4, 236, 102, 101, 162, 192, 170, 182, 74, 98, 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