Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3c59420fa01e8b67c1082a3054980232809b14c055fcd348bca44460e9a75ca

Tx prefix hash: 39ddc1026b5097b2b596cb1d365ecf2c8d1455779dc1cee0504e6593de7f7099
Tx public key: 5c6c5911619661774ad8b8b0863d08e172a6d46600e9c0f87ec7902b6163d50e
Timestamp: 1581948077 Timestamp [UCT]: 2020-02-17 14:01:17 Age [y:d:h:m:s]: 04:350:08:49:47
Block: 66776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1142597 RingCT/type: yes/0
Extra: 015c6c5911619661774ad8b8b0863d08e172a6d46600e9c0f87ec7902b6163d50e02110000000203d36d11000000000000000000

1 output(s) for total of 368.760334599000 dcy

stealth address amount amount idx
00: 7f7bfba07c87b122b62f53b3e3a15654f7ea16ba21d4394175b5c1774bba0b58 368.760334599000 122966 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": 66786, "vin": [ { "gen": { "height": 66776 } } ], "vout": [ { "amount": 368760334599, "target": { "key": "7f7bfba07c87b122b62f53b3e3a15654f7ea16ba21d4394175b5c1774bba0b58" } } ], "extra": [ 1, 92, 108, 89, 17, 97, 150, 97, 119, 74, 216, 184, 176, 134, 61, 8, 225, 114, 166, 212, 102, 0, 233, 192, 248, 126, 199, 144, 43, 97, 99, 213, 14, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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