Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 288c135a2bdc29b127f35d5960ce23ec95e0fc36d201ef42559d9c45dd81dbdb

Tx prefix hash: fd1635a35715f04d092b16de9d9fac16474e83df9cee3ef913d12cd56fafb08b
Tx public key: dcf8a8b0adad18dbb599f4181411f046b9868d85d3a719cb791de8b09140ae1b
Timestamp: 1724535319 Timestamp [UCT]: 2024-08-24 21:35:19 Age [y:d:h:m:s]: 00:219:02:27:50
Block: 1095180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156434 RingCT/type: yes/0
Extra: 01dcf8a8b0adad18dbb599f4181411f046b9868d85d3a719cb791de8b09140ae1b021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c52b89f23a7a51c0fb1611347e1706b744aaf0b711ab9ee6080caf580ad4fd3 0.600000000000 1570329 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": 1095190, "vin": [ { "gen": { "height": 1095180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c52b89f23a7a51c0fb1611347e1706b744aaf0b711ab9ee6080caf580ad4fd3" } } ], "extra": [ 1, 220, 248, 168, 176, 173, 173, 24, 219, 181, 153, 244, 24, 20, 17, 240, 70, 185, 134, 141, 133, 211, 167, 25, 203, 121, 29, 232, 176, 145, 64, 174, 27, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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