Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ab660f9f8b90522483b1078e991defef71ae0c3d51e3797b5e1895c669eb811

Tx prefix hash: 74509c5a1e346e7f9296e330ff7d388b33dfe47e82a8014e2ba37ab4d7606905
Tx public key: 60fc2065ef181fc56d30c7580d9feef485559d41bfe83b432dc25c178db7578b
Timestamp: 1720563429 Timestamp [UCT]: 2024-07-09 22:17:09 Age [y:d:h:m:s]: 01:132:06:20:10
Block: 1062229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353055 RingCT/type: yes/0
Extra: 0160fc2065ef181fc56d30c7580d9feef485559d41bfe83b432dc25c178db7578b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9553b644b0279376feb1a2c01c99789f7ae8d5f1ee635a072cf352844d7c0e0b 0.600000000000 1532730 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": 1062239, "vin": [ { "gen": { "height": 1062229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9553b644b0279376feb1a2c01c99789f7ae8d5f1ee635a072cf352844d7c0e0b" } } ], "extra": [ 1, 96, 252, 32, 101, 239, 24, 31, 197, 109, 48, 199, 88, 13, 159, 238, 244, 133, 85, 157, 65, 191, 232, 59, 67, 45, 194, 92, 23, 141, 183, 87, 139, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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