Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c654147e619e04f7b17ccc4d5cc97cbdbdcfba7bcfbe3bff03ae60789cd53097

Tx prefix hash: 7dbe9e02525c54e6b01f633ac04394d665e21b0043204bff7e150e3198df2098
Tx public key: f710e96bd45672c83afe5f46a262ef5e0f75848f497d8c3b3fec1d382c837904
Timestamp: 1725187334 Timestamp [UCT]: 2024-09-01 10:42:14 Age [y:d:h:m:s]: 00:264:16:05:33
Block: 1100566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189048 RingCT/type: yes/0
Extra: 01f710e96bd45672c83afe5f46a262ef5e0f75848f497d8c3b3fec1d382c83790402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ed63ec7b07ebf0d3a88ee1a48810c4bb822c234a33cb2bcd1a36862c8ffdb75 0.600000000000 1576545 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": 1100576, "vin": [ { "gen": { "height": 1100566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ed63ec7b07ebf0d3a88ee1a48810c4bb822c234a33cb2bcd1a36862c8ffdb75" } } ], "extra": [ 1, 247, 16, 233, 107, 212, 86, 114, 200, 58, 254, 95, 70, 162, 98, 239, 94, 15, 117, 132, 143, 73, 125, 140, 59, 63, 236, 29, 56, 44, 131, 121, 4, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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