Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18a8a5be949e40c672a835466d819b7c660887a851d96630892af587c0cd8707

Tx prefix hash: 07b348a78a5acd811628d208a1448250f5b69ed07d2e672a37240fc3e8086e67
Tx public key: a40eec920a9b4e54066099f8c83e3ce33c515f4a3c90af16f3a79a88ee7475b3
Timestamp: 1712128206 Timestamp [UCT]: 2024-04-03 07:10:06 Age [y:d:h:m:s]: 01:210:19:07:42
Block: 992260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409365 RingCT/type: yes/0
Extra: 01a40eec920a9b4e54066099f8c83e3ce33c515f4a3c90af16f3a79a88ee7475b302110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf48a1f63ccee4562f64b7b96f815ff636fc7268eb49765b5a1cba3ff987a071 0.600000000000 1452600 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": 992270, "vin": [ { "gen": { "height": 992260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf48a1f63ccee4562f64b7b96f815ff636fc7268eb49765b5a1cba3ff987a071" } } ], "extra": [ 1, 164, 14, 236, 146, 10, 155, 78, 84, 6, 96, 153, 248, 200, 62, 60, 227, 60, 81, 95, 74, 60, 144, 175, 22, 243, 167, 154, 136, 238, 116, 117, 179, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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