Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32dc0203afe2cef219bc53710a5b2b56612fb044f3d61aed27c6753cb3670e41

Tx prefix hash: 3a166ede419cdc60f7f035feffc751eb5085e4e5fde02231d9eb9bfb3117d756
Tx public key: b57f7f5230a9c009a0909956ae33d3e4bddd838157e644e5aae4d1f146d77764
Timestamp: 1705481738 Timestamp [UCT]: 2024-01-17 08:55:38 Age [y:d:h:m:s]: 01:080:14:48:06
Block: 937174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318701 RingCT/type: yes/0
Extra: 01b57f7f5230a9c009a0909956ae33d3e4bddd838157e644e5aae4d1f146d777640211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6416e3bad4169b9f7f65d380cd9462405f9ec7fb585e838241643f0886c3a6b1 0.600000000000 1395218 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": 937184, "vin": [ { "gen": { "height": 937174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6416e3bad4169b9f7f65d380cd9462405f9ec7fb585e838241643f0886c3a6b1" } } ], "extra": [ 1, 181, 127, 127, 82, 48, 169, 192, 9, 160, 144, 153, 86, 174, 51, 211, 228, 189, 221, 131, 129, 87, 230, 68, 229, 170, 228, 209, 241, 70, 215, 119, 100, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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