Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e902ea79eec84b3323b28000944a08b23adb6f933a50e67dd48b5eb2727a25d

Tx prefix hash: ef7c9e82d7f792b82f8991b17184163f307d1db854301081eaed94990db161a9
Tx public key: b791eb04eb5af7f4b7176e3acf14354d2e523bd5a89a9d919f8897dd152fc0a1
Timestamp: 1738527606 Timestamp [UCT]: 2025-02-02 20:20:06 Age [y:d:h:m:s]: 00:337:00:43:45
Block: 1210719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238729 RingCT/type: yes/0
Extra: 01b791eb04eb5af7f4b7176e3acf14354d2e523bd5a89a9d919f8897dd152fc0a1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e47130926e8e9bdbe17b68a3214790e7d6fd47ef01fb0da525a4d161a436a65 0.600000000000 1697474 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": 1210729, "vin": [ { "gen": { "height": 1210719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e47130926e8e9bdbe17b68a3214790e7d6fd47ef01fb0da525a4d161a436a65" } } ], "extra": [ 1, 183, 145, 235, 4, 235, 90, 247, 244, 183, 23, 110, 58, 207, 20, 53, 77, 46, 82, 59, 213, 168, 154, 157, 145, 159, 136, 151, 221, 21, 47, 192, 161, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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