Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 489f22f5041a668fd4285265b11ddad60dfe1c5f4a902d796d19e1c9075bb200

Tx prefix hash: f45207fb953e16d90effb3dfd3d3a4d2b04094c0df48db46649b9823d84c6d73
Tx public key: 40ac5b42277057988ad7bd15b87fa65fe620d196d3da9c0edf86d2b565c8650a
Timestamp: 1710320874 Timestamp [UCT]: 2024-03-13 09:07:54 Age [y:d:h:m:s]: 01:023:13:04:39
Block: 977319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277802 RingCT/type: yes/0
Extra: 0140ac5b42277057988ad7bd15b87fa65fe620d196d3da9c0edf86d2b565c8650a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8312b17375591bc5a72611ac19fe9f606b17d488f9ef5f53c6062b8c34a50802 0.600000000000 1437320 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": 977329, "vin": [ { "gen": { "height": 977319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8312b17375591bc5a72611ac19fe9f606b17d488f9ef5f53c6062b8c34a50802" } } ], "extra": [ 1, 64, 172, 91, 66, 39, 112, 87, 152, 138, 215, 189, 21, 184, 127, 166, 95, 230, 32, 209, 150, 211, 218, 156, 14, 223, 134, 210, 181, 101, 200, 101, 10, 2, 17, 0, 0, 0, 3, 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