Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 999b3f869c758a32cdf9eac52906f8bbecc540b0ef9817fcc81460bddcf9ed75

Tx prefix hash: fccd890b389a918b16ea659f179c4ac896f2efdc2947b6e55b007b4d106ebee0
Tx public key: 9c1519e448de9c3c5928c15fa67408bb09a8e93bc32c88d25a51843479b43e5b
Timestamp: 1712653922 Timestamp [UCT]: 2024-04-09 09:12:02 Age [y:d:h:m:s]: 00:359:14:10:03
Block: 996627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257102 RingCT/type: yes/0
Extra: 019c1519e448de9c3c5928c15fa67408bb09a8e93bc32c88d25a51843479b43e5b02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aa65ace6e66152eab73c4ee88fc7d5f71987b7c0ac7f7da6e2cf7cd3a215db0 0.600000000000 1457051 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": 996637, "vin": [ { "gen": { "height": 996627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aa65ace6e66152eab73c4ee88fc7d5f71987b7c0ac7f7da6e2cf7cd3a215db0" } } ], "extra": [ 1, 156, 21, 25, 228, 72, 222, 156, 60, 89, 40, 193, 95, 166, 116, 8, 187, 9, 168, 233, 59, 195, 44, 136, 210, 90, 81, 132, 52, 121, 180, 62, 91, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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