Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb166ae19b9149150f206adfc32fe011f6410ba30cbd138b0fb9009d4ba7efab

Tx prefix hash: 5ec3cd55fd991f5a3ddfce956e5200841302d7ac20ffc05f0fb1a7d24efeb6ac
Tx public key: 0ff5c11e2446f3313038023a0abf186ab19b5ed5bb72c8b6e6e0180c68bb5a08
Timestamp: 1729839133 Timestamp [UCT]: 2024-10-25 06:52:13 Age [y:d:h:m:s]: 00:151:04:40:11
Block: 1139086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107855 RingCT/type: yes/0
Extra: 010ff5c11e2446f3313038023a0abf186ab19b5ed5bb72c8b6e6e0180c68bb5a080211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6832a26e610eab977fade9a04c3eed46a4f4b41fa759e504cbb0a422ac518fa6 0.600000000000 1622847 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": 1139096, "vin": [ { "gen": { "height": 1139086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6832a26e610eab977fade9a04c3eed46a4f4b41fa759e504cbb0a422ac518fa6" } } ], "extra": [ 1, 15, 245, 193, 30, 36, 70, 243, 49, 48, 56, 2, 58, 10, 191, 24, 106, 177, 155, 94, 213, 187, 114, 200, 182, 230, 224, 24, 12, 104, 187, 90, 8, 2, 17, 0, 0, 0, 4, 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