Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82bfb54935c857a9fb520abaadfce5c28493a6baa0a376be5ea9d61c4833993b

Tx prefix hash: 96b23b546873db1c54f86fc1cbf2431461ddb16a4a8153e366d26f04282fc5ce
Tx public key: f239e8d3bca307f1247f971c4194ac12bf06850615f7e269c3251dcae015e135
Timestamp: 1722770789 Timestamp [UCT]: 2024-08-04 11:26:29 Age [y:d:h:m:s]: 00:233:13:06:46
Block: 1080526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166792 RingCT/type: yes/0
Extra: 01f239e8d3bca307f1247f971c4194ac12bf06850615f7e269c3251dcae015e13502110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fcc3090d07dd5ef202e3958d223f165dec3af1c7a268e563b416d6becdbf783 0.600000000000 1553919 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": 1080536, "vin": [ { "gen": { "height": 1080526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fcc3090d07dd5ef202e3958d223f165dec3af1c7a268e563b416d6becdbf783" } } ], "extra": [ 1, 242, 57, 232, 211, 188, 163, 7, 241, 36, 127, 151, 28, 65, 148, 172, 18, 191, 6, 133, 6, 21, 247, 226, 105, 195, 37, 29, 202, 224, 21, 225, 53, 2, 17, 0, 0, 0, 12, 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