Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c55f7be91bdef69aff3f667a6f0f7c643c2b5664e8c5728e170b185b36f2d34

Tx prefix hash: e101eb30a1e39f0ab7ac22e42b92d4d769324eef02629289bf4c7dd43661e413
Tx public key: 9ff2cc26d01209a5cb820c920bfc42722fe85110d65f1c4c7cb30e23bbcb7ad0
Timestamp: 1581430398 Timestamp [UCT]: 2020-02-11 14:13:18 Age [y:d:h:m:s]: 04:319:14:58:26
Block: 62897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120477 RingCT/type: yes/0
Extra: 019ff2cc26d01209a5cb820c920bfc42722fe85110d65f1c4c7cb30e23bbcb7ad002110000000112c4732d000000000000000000

1 output(s) for total of 379.836716736000 dcy

stealth address amount amount idx
00: 2d18c18a237bc316c5c9a38a2cd087b644b6a2a91395fce75e4d4a62e447ecaa 379.836716736000 115935 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": 62907, "vin": [ { "gen": { "height": 62897 } } ], "vout": [ { "amount": 379836716736, "target": { "key": "2d18c18a237bc316c5c9a38a2cd087b644b6a2a91395fce75e4d4a62e447ecaa" } } ], "extra": [ 1, 159, 242, 204, 38, 208, 18, 9, 165, 203, 130, 12, 146, 11, 252, 66, 114, 47, 232, 81, 16, 214, 95, 28, 76, 124, 179, 14, 35, 187, 203, 122, 208, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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