Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5633d2391b19385b5a028c2e894e8bfdcad5db0f0f463f53b8f0ab1c502060a

Tx prefix hash: 49a3176e96aa025dfb54b410f70ecb536e75679d70799b22044e9428d6080565
Tx public key: b9d53a989284517a5b876b1fed873a73d131524292848c5487aa54a583c6b830
Timestamp: 1717351119 Timestamp [UCT]: 2024-06-02 17:58:39 Age [y:d:h:m:s]: 01:183:06:06:58
Block: 1035604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389579 RingCT/type: yes/0
Extra: 01b9d53a989284517a5b876b1fed873a73d131524292848c5487aa54a583c6b83002110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0787ab704e9c1ad6102a7b4a49ad6554cd0f77a5409b53e898b052a0fc7278d0 0.600000000000 1504125 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": 1035614, "vin": [ { "gen": { "height": 1035604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0787ab704e9c1ad6102a7b4a49ad6554cd0f77a5409b53e898b052a0fc7278d0" } } ], "extra": [ 1, 185, 213, 58, 152, 146, 132, 81, 122, 91, 135, 107, 31, 237, 135, 58, 115, 209, 49, 82, 66, 146, 132, 140, 84, 135, 170, 84, 165, 131, 198, 184, 48, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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