Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70fff29252a55e7fea2b397e6fedef5766b00ee2a1e328333600d6201f7fdba0

Tx prefix hash: fbf2876e43a183727ee90cf5f1f22c03ee175571968cfb1492fe3232d7d22f83
Tx public key: 56ca5dbef5aec63f60c78a3b1ad909eb94b9fe8ad23a6ab5c69bd1fd6d6d7641
Timestamp: 1727093783 Timestamp [UCT]: 2024-09-23 12:16:23 Age [y:d:h:m:s]: 00:206:17:30:30
Block: 1116372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147566 RingCT/type: yes/0
Extra: 0156ca5dbef5aec63f60c78a3b1ad909eb94b9fe8ad23a6ab5c69bd1fd6d6d7641021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66e940a77407e4326b432a70f1a4212925726641ae1b26525192203f42a1cfde 0.600000000000 1596827 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": 1116382, "vin": [ { "gen": { "height": 1116372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66e940a77407e4326b432a70f1a4212925726641ae1b26525192203f42a1cfde" } } ], "extra": [ 1, 86, 202, 93, 190, 245, 174, 198, 63, 96, 199, 138, 59, 26, 217, 9, 235, 148, 185, 254, 138, 210, 58, 106, 181, 198, 155, 209, 253, 109, 109, 118, 65, 2, 17, 0, 0, 0, 6, 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