Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41c4d0cc6ff96f17ed24abd0ecc58f71c6f47d37b9a2fbc76ad328266067964e

Tx prefix hash: cd3f5f276e63051d6c8f5c2f7553f473c50675e6b4243c5dab416468921da062
Tx public key: 90ea921350fad7db53218269e2037cf731fbaa0deb45fdc969f162284ccd36b8
Timestamp: 1577741817 Timestamp [UCT]: 2019-12-30 21:36:57 Age [y:d:h:m:s]: 05:007:06:07:36
Block: 35337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155140 RingCT/type: yes/0
Extra: 0190ea921350fad7db53218269e2037cf731fbaa0deb45fdc969f162284ccd36b802110000007bc3a1a09f000000000000000000

1 output(s) for total of 468.721316039000 dcy

stealth address amount amount idx
00: 4f708a5fce4e4fd8e646da7183b3f87e42df2f3e64e94bdaa05c0dff243e03a4 468.721316039000 59525 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": 35347, "vin": [ { "gen": { "height": 35337 } } ], "vout": [ { "amount": 468721316039, "target": { "key": "4f708a5fce4e4fd8e646da7183b3f87e42df2f3e64e94bdaa05c0dff243e03a4" } } ], "extra": [ 1, 144, 234, 146, 19, 80, 250, 215, 219, 83, 33, 130, 105, 226, 3, 124, 247, 49, 251, 170, 13, 235, 69, 253, 201, 105, 241, 98, 40, 76, 205, 54, 184, 2, 17, 0, 0, 0, 123, 195, 161, 160, 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