Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 083ed76251ccf01c49841196e17f10a214319bab654c704b013e62cb69b1edfd

Tx prefix hash: 9b7d08dcbfe0ca0d11bfde340537abc0d5770de66bad3eba4d1c8e09590edd60
Tx public key: 9fffcf423b934aa5582d58cc1c9735c23d3cbe66fa60b401edd5f8ec3f77296f
Timestamp: 1717195311 Timestamp [UCT]: 2024-05-31 22:41:51 Age [y:d:h:m:s]: 01:221:05:00:09
Block: 1034306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416760 RingCT/type: yes/0
Extra: 019fffcf423b934aa5582d58cc1c9735c23d3cbe66fa60b401edd5f8ec3f77296f02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6da1dc11116241271848e73d0b87d583582114a0a856217f41869cfe7b44d23 0.600000000000 1502807 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": 1034316, "vin": [ { "gen": { "height": 1034306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6da1dc11116241271848e73d0b87d583582114a0a856217f41869cfe7b44d23" } } ], "extra": [ 1, 159, 255, 207, 66, 59, 147, 74, 165, 88, 45, 88, 204, 28, 151, 53, 194, 61, 60, 190, 102, 250, 96, 180, 1, 237, 213, 248, 236, 63, 119, 41, 111, 2, 17, 0, 0, 0, 11, 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