Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efee0bddc2a73c28dc078fffd05bffda882d52fadda45f57f263b4f67275a152

Tx prefix hash: 8d868e394c86bd22d6293421d7742c3fd79e5c36eb57b4f4d16bc10e7075fdaf
Tx public key: 3cebfdb43e4267c61968c4bf35b1f017f6bcd4e8977a78bada67647cc5637112
Timestamp: 1590639089 Timestamp [UCT]: 2020-05-28 04:11:29 Age [y:d:h:m:s]: 04:281:01:03:01
Block: 103729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128000 RingCT/type: yes/0
Extra: 013cebfdb43e4267c61968c4bf35b1f017f6bcd4e8977a78bada67647cc5637112021100000049d81c26c0000000000000000000

1 output(s) for total of 278.175283627000 dcy

stealth address amount amount idx
00: 0c63d8369a42022e8980a775bea0b7a6840443dbb40d2e19ca48dd7e1e30b165 278.175283627000 181944 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": 103739, "vin": [ { "gen": { "height": 103729 } } ], "vout": [ { "amount": 278175283627, "target": { "key": "0c63d8369a42022e8980a775bea0b7a6840443dbb40d2e19ca48dd7e1e30b165" } } ], "extra": [ 1, 60, 235, 253, 180, 62, 66, 103, 198, 25, 104, 196, 191, 53, 177, 240, 23, 246, 188, 212, 232, 151, 122, 120, 186, 218, 103, 100, 124, 197, 99, 113, 18, 2, 17, 0, 0, 0, 73, 216, 28, 38, 192, 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