Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe498f00d232752c35b1cbdc2b2aef29593627a0b54f7d62f63d5defbf540811

Tx prefix hash: a43a0db879f44bb1a2e4112d94ede0d248bbb6cbdc0cd98f356c25b82b4a68bb
Tx public key: cc172832d4360caeb195f449d1e11b32d120e7c99f1c53a5813626c687525640
Timestamp: 1580113864 Timestamp [UCT]: 2020-01-27 08:31:04 Age [y:d:h:m:s]: 05:106:01:31:26
Block: 53718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1226799 RingCT/type: yes/0
Extra: 01cc172832d4360caeb195f449d1e11b32d120e7c99f1c53a5813626c6875256400211000000014943cd9f000000000000000000

1 output(s) for total of 407.390403126000 dcy

stealth address amount amount idx
00: 0de38230b65b2e83106b589f8ec637dfb04c2f9a8ce25b2d2be075fca70764b4 407.390403126000 99590 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": 53728, "vin": [ { "gen": { "height": 53718 } } ], "vout": [ { "amount": 407390403126, "target": { "key": "0de38230b65b2e83106b589f8ec637dfb04c2f9a8ce25b2d2be075fca70764b4" } } ], "extra": [ 1, 204, 23, 40, 50, 212, 54, 12, 174, 177, 149, 244, 73, 209, 225, 27, 50, 209, 32, 231, 201, 159, 28, 83, 165, 129, 54, 38, 198, 135, 82, 86, 64, 2, 17, 0, 0, 0, 1, 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