Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 594f3c6ee16a7293c3e16b12c3026f7b0d6acedd9daf4a7c62c5bffefbff3414

Tx prefix hash: 7c28c0e8a6b307f045c4e7feb507ca7005bb2e7f5a9311bfde71898f308de44a
Tx public key: b765989a2d911b8c7ffe9e1a59117d27520b0457b82d415916e4a42bf137e35f
Timestamp: 1710392875 Timestamp [UCT]: 2024-03-14 05:07:55 Age [y:d:h:m:s]: 01:039:12:06:33
Block: 977926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289213 RingCT/type: yes/0
Extra: 01b765989a2d911b8c7ffe9e1a59117d27520b0457b82d415916e4a42bf137e35f02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec0c2963f1b4cf7a7cae91bfc0c35fe3055809bdc5316bbedf6fca8425e43e3b 0.600000000000 1437935 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": 977936, "vin": [ { "gen": { "height": 977926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec0c2963f1b4cf7a7cae91bfc0c35fe3055809bdc5316bbedf6fca8425e43e3b" } } ], "extra": [ 1, 183, 101, 152, 154, 45, 145, 27, 140, 127, 254, 158, 26, 89, 17, 125, 39, 82, 11, 4, 87, 184, 45, 65, 89, 22, 228, 164, 43, 241, 55, 227, 95, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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