Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9407122aa7e3c20080705da4407ca029d8fe1ae31a1b4cc88f16e16ffec639a1

Tx prefix hash: 88b129035fd05b922d63495140ebf174c55f79998f61c2b9f8646c9b2af49ece
Tx public key: b14ff413ac1f0277a9a9b5477204cd079d07ad0ea26452e2b9ea1311f6c4d892
Timestamp: 1722723526 Timestamp [UCT]: 2024-08-03 22:18:46 Age [y:d:h:m:s]: 00:300:06:54:26
Block: 1080133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214562 RingCT/type: yes/0
Extra: 01b14ff413ac1f0277a9a9b5477204cd079d07ad0ea26452e2b9ea1311f6c4d892021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90b04ff778c6af14618e299e6580deb9649e3caa7e137474e6a2988ea063c167 0.600000000000 1553378 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": 1080143, "vin": [ { "gen": { "height": 1080133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90b04ff778c6af14618e299e6580deb9649e3caa7e137474e6a2988ea063c167" } } ], "extra": [ 1, 177, 79, 244, 19, 172, 31, 2, 119, 169, 169, 181, 71, 114, 4, 205, 7, 157, 7, 173, 14, 162, 100, 82, 226, 185, 234, 19, 17, 246, 196, 216, 146, 2, 17, 0, 0, 0, 4, 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