Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 028a7e9b2c1aad547a718d5ee3dc1baf825cb6956457fe5806db82c8aa862c6e

Tx prefix hash: b779ddb05ba80135c9ba2410d97afe94d06fc1b8394d083f9442814d80bbc563
Tx public key: f6c54add49e5b75eaf770c69061bc883b2fe2054d411e928d806aff6689c180f
Timestamp: 1594748397 Timestamp [UCT]: 2020-07-14 17:39:57 Age [y:d:h:m:s]: 04:238:22:43:06
Block: 117635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118016 RingCT/type: yes/0
Extra: 01f6c54add49e5b75eaf770c69061bc883b2fe2054d411e928d806aff6689c180f021100000019d81c26c0000000000000000000

1 output(s) for total of 250.169676055000 dcy

stealth address amount amount idx
00: 537b708f1434cc022b424b88cfe030aee6fcc100787ff58dce3120eea4c41e25 250.169676055000 200973 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": 117645, "vin": [ { "gen": { "height": 117635 } } ], "vout": [ { "amount": 250169676055, "target": { "key": "537b708f1434cc022b424b88cfe030aee6fcc100787ff58dce3120eea4c41e25" } } ], "extra": [ 1, 246, 197, 74, 221, 73, 229, 183, 94, 175, 119, 12, 105, 6, 27, 200, 131, 178, 254, 32, 84, 212, 17, 233, 40, 216, 6, 175, 246, 104, 156, 24, 15, 2, 17, 0, 0, 0, 25, 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