Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b68fdca0e087b7c4377175769cd902548d140a966ba793375c905fbf80d8b199

Tx prefix hash: b50763b664960fa8ebfcc4b316a6d713f48f6d26ba9e7cf959878cf834cd216d
Tx public key: 0ba41857bd6385a133c6ea63025de80612e75db41d78f9d43d68bac6aa2b64cd
Timestamp: 1719256284 Timestamp [UCT]: 2024-06-24 19:11:24 Age [y:d:h:m:s]: 00:269:02:36:14
Block: 1051376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192313 RingCT/type: yes/0
Extra: 010ba41857bd6385a133c6ea63025de80612e75db41d78f9d43d68bac6aa2b64cd02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bdc2dd83df2c71f1c2f975068e846be1719c3a3d48ef6a1f426aa55ddcf5011 0.600000000000 1521687 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": 1051386, "vin": [ { "gen": { "height": 1051376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bdc2dd83df2c71f1c2f975068e846be1719c3a3d48ef6a1f426aa55ddcf5011" } } ], "extra": [ 1, 11, 164, 24, 87, 189, 99, 133, 161, 51, 198, 234, 99, 2, 93, 232, 6, 18, 231, 93, 180, 29, 120, 249, 212, 61, 104, 186, 198, 170, 43, 100, 205, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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