Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ed42b0ea091823e3b1e0ba63a02d7206f4dae8e87f451a7ffcb272a3cb91aa

Tx prefix hash: 5532f9dfcfdc0160dce53078025a07c0bc9d206862259e43c3080ee2fe1d4889
Tx public key: 8a98eacdb992594edfb4e8e8d45e451219075fb9e710efe7f4a6273613fbe5dd
Timestamp: 1575851288 Timestamp [UCT]: 2019-12-09 00:28:08 Age [y:d:h:m:s]: 04:353:03:14:55
Block: 23427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137710 RingCT/type: yes/0
Extra: 018a98eacdb992594edfb4e8e8d45e451219075fb9e710efe7f4a6273613fbe5dd0211000000054943cd9f000000000000000000

1 output(s) for total of 513.333955339000 dcy

stealth address amount amount idx
00: b3e35df36bbe7f4a62a5f36110b3badd6408133127a63f47d6bd6a25959cf665 513.333955339000 37716 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": 23437, "vin": [ { "gen": { "height": 23427 } } ], "vout": [ { "amount": 513333955339, "target": { "key": "b3e35df36bbe7f4a62a5f36110b3badd6408133127a63f47d6bd6a25959cf665" } } ], "extra": [ 1, 138, 152, 234, 205, 185, 146, 89, 78, 223, 180, 232, 232, 212, 94, 69, 18, 25, 7, 95, 185, 231, 16, 239, 231, 244, 166, 39, 54, 19, 251, 229, 221, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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