Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c075898428d0d465bc0c1dc30e5a4e0ebce94cac661956d964fbfdc083d153

Tx prefix hash: a8bc5e4c80e3f4e9e16100139a522c8d8b1c114ac973c1a48238708148ff5042
Tx public key: 92f96a19debcbebbfbea2d1432a59a35f7c1fa98a8a102c6ac5ddebdd6827d13
Timestamp: 1694768592 Timestamp [UCT]: 2023-09-15 09:03:12 Age [y:d:h:m:s]: 01:199:01:34:50
Block: 848556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403357 RingCT/type: yes/0
Extra: 0192f96a19debcbebbfbea2d1432a59a35f7c1fa98a8a102c6ac5ddebdd6827d13021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.947069343000 dcy

stealth address amount amount idx
00: 9e251c1dd729139c41a05f5e5eddc0d2ab567b5dfe7367659709e00e7a7b731b 0.947069343000 1302168 of 0

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": 848566, "vin": [ { "gen": { "height": 848556 } } ], "vout": [ { "amount": 947069343, "target": { "key": "9e251c1dd729139c41a05f5e5eddc0d2ab567b5dfe7367659709e00e7a7b731b" } } ], "extra": [ 1, 146, 249, 106, 25, 222, 188, 190, 187, 251, 234, 45, 20, 50, 165, 154, 53, 247, 193, 250, 152, 168, 161, 2, 198, 172, 93, 222, 189, 214, 130, 125, 19, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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