Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f8d55ec5ae318fb8a06c84a5468b41a1a4d1d816da72f47d9fe43ca8a1fbff1

Tx prefix hash: f252ef71112a8ac0c236b3e2b7c6f1fdab26e62a56db66bceaa570f0da825bb2
Tx public key: 007b68e3fab09d109ae3d89a734ad79355615339daf63c8b1fa5e4ab9cb6d346
Timestamp: 1703657232 Timestamp [UCT]: 2023-12-27 06:07:12 Age [y:d:h:m:s]: 01:117:21:27:55
Block: 922058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345386 RingCT/type: yes/0
Extra: 01007b68e3fab09d109ae3d89a734ad79355615339daf63c8b1fa5e4ab9cb6d34602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f01868c37413f5b535f4095416c313febf41f0de7d68fdcce7a374b0db658bd3 0.600000000000 1379752 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": 922068, "vin": [ { "gen": { "height": 922058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f01868c37413f5b535f4095416c313febf41f0de7d68fdcce7a374b0db658bd3" } } ], "extra": [ 1, 0, 123, 104, 227, 250, 176, 157, 16, 154, 227, 216, 154, 115, 74, 215, 147, 85, 97, 83, 57, 218, 246, 60, 139, 31, 165, 228, 171, 156, 182, 211, 70, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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