Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27db7786dbd184e961ddc49a1458ae672f7cca119a080da2850facc323c2fb8c

Tx prefix hash: d98159fa7d5555bd43c5fada950c50cd089f2d0d3d27a50b78641fa4e8c2df6f
Tx public key: 74a770be4a1807b9b2be72e95fd5d202a2ad4b7df05cd26ef086659336e12ffd
Timestamp: 1714108384 Timestamp [UCT]: 2024-04-26 05:13:04 Age [y:d:h:m:s]: 00:258:16:45:04
Block: 1008709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185172 RingCT/type: yes/0
Extra: 0174a770be4a1807b9b2be72e95fd5d202a2ad4b7df05cd26ef086659336e12ffd02110000000618ec9060000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1048ed0f9bc55a35e1ce413103fa27d20c97e6e50e237f5c1dedf7121818be6c 0.600000000000 1470187 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": 1008719, "vin": [ { "gen": { "height": 1008709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1048ed0f9bc55a35e1ce413103fa27d20c97e6e50e237f5c1dedf7121818be6c" } } ], "extra": [ 1, 116, 167, 112, 190, 74, 24, 7, 185, 178, 190, 114, 233, 95, 213, 210, 2, 162, 173, 75, 125, 240, 92, 210, 110, 240, 134, 101, 147, 54, 225, 47, 253, 2, 17, 0, 0, 0, 6, 24, 236, 144, 96, 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