Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4836921a690182d9c21b01ff42ff0278b9ee43c4245476f6a2f4ade7f2c024

Tx prefix hash: ff67ea0ff54b81b35da276d7196e673039eb4b16f753f46c59f8947deeb11ed1
Tx public key: 3002730a73767eca299d6c10f8829fc9359a8e535addd76b1c5298a1ca4f8319
Timestamp: 1705704447 Timestamp [UCT]: 2024-01-19 22:47:27 Age [y:d:h:m:s]: 01:293:09:10:13
Block: 939009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468506 RingCT/type: yes/0
Extra: 013002730a73767eca299d6c10f8829fc9359a8e535addd76b1c5298a1ca4f83190211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d61af467e00ab14b3497ec6c7dfb01a9b5c9bd3d317ba2878e69229cebec314a 0.600000000000 1397093 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": 939019, "vin": [ { "gen": { "height": 939009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d61af467e00ab14b3497ec6c7dfb01a9b5c9bd3d317ba2878e69229cebec314a" } } ], "extra": [ 1, 48, 2, 115, 10, 115, 118, 126, 202, 41, 157, 108, 16, 248, 130, 159, 201, 53, 154, 142, 83, 90, 221, 215, 107, 28, 82, 152, 161, 202, 79, 131, 25, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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