Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37493bd9597c362761840ad3c2cbfdc1b3ca2d861a7e6c8bee34942f60fcca18

Tx prefix hash: 2199b2e81178d52f7f8adbb4cdcc2ffbf6739670305c4bd797b28d0b8eeb3b54
Tx public key: b80cb6f7b11acb9a6dd2a92b809a86d34d2307e6ddd99b16407069489931ef71
Timestamp: 1583748003 Timestamp [UCT]: 2020-03-09 10:00:03 Age [y:d:h:m:s]: 04:302:15:51:49
Block: 78937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111481 RingCT/type: yes/0
Extra: 01b80cb6f7b11acb9a6dd2a92b809a86d34d2307e6ddd99b16407069489931ef71021100000001995a6b02000000000000000000

1 output(s) for total of 336.091274021000 dcy

stealth address amount amount idx
00: b21044c57501153414bf3c79cec3d3b3723015cb6a4bbc8c5dc3b896205035ae 336.091274021000 144625 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": 78947, "vin": [ { "gen": { "height": 78937 } } ], "vout": [ { "amount": 336091274021, "target": { "key": "b21044c57501153414bf3c79cec3d3b3723015cb6a4bbc8c5dc3b896205035ae" } } ], "extra": [ 1, 184, 12, 182, 247, 177, 26, 203, 154, 109, 210, 169, 43, 128, 154, 134, 211, 77, 35, 7, 230, 221, 217, 155, 22, 64, 112, 105, 72, 153, 49, 239, 113, 2, 17, 0, 0, 0, 1, 153, 90, 107, 2, 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