Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ee49e75d190bbd73d05b81abaf3e3881c1e1ec5cd7e83d269be625af313d492

Tx prefix hash: 89f8bc9f372eefa646481edc1e89e8000ba364da7e70ef5694fd7748430cb163
Tx public key: 6c090587964d9d4b0b43cd0f95c134b800cb32fa3ffecd1470217aee052a8ac1
Timestamp: 1676542712 Timestamp [UCT]: 2023-02-16 10:18:32 Age [y:d:h:m:s]: 02:008:23:54:27
Block: 698153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527996 RingCT/type: yes/0
Extra: 016c090587964d9d4b0b43cd0f95c134b800cb32fa3ffecd1470217aee052a8ac102110000000174b6d784000000000000000000

1 output(s) for total of 2.983521761000 dcy

stealth address amount amount idx
00: 8f01900bf7498a0881ff35e9f4a6d5adc9c2799d99a5a640e113dd2281f4d6e2 2.983521761000 1141436 of 0

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": 698163, "vin": [ { "gen": { "height": 698153 } } ], "vout": [ { "amount": 2983521761, "target": { "key": "8f01900bf7498a0881ff35e9f4a6d5adc9c2799d99a5a640e113dd2281f4d6e2" } } ], "extra": [ 1, 108, 9, 5, 135, 150, 77, 157, 75, 11, 67, 205, 15, 149, 193, 52, 184, 0, 203, 50, 250, 63, 254, 205, 20, 112, 33, 122, 238, 5, 42, 138, 193, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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