Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 510c3fd93add0764f657a8e7b9b9db87d6c4c2067ffd6b53e4edb5c32451ca07

Tx prefix hash: ccd5f19867f8d52376a26f1fadcceadb332a420c60571d18b1790d505ed8fbf0
Tx public key: e01e2e92690f07136575da44c880fdbcfe62bdfaf2a76286fbbde96f1de5886c
Timestamp: 1582098339 Timestamp [UCT]: 2020-02-19 07:45:39 Age [y:d:h:m:s]: 05:082:10:51:12
Block: 67920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1212133 RingCT/type: yes/0
Extra: 01e01e2e92690f07136575da44c880fdbcfe62bdfaf2a76286fbbde96f1de5886c021100000004026b59f3000000000000000000

1 output(s) for total of 365.555777167000 dcy

stealth address amount amount idx
00: 3aa6d731b027196dd9ebafc2ae8b1af9f183bab1d7c28399911d921262b63472 365.555777167000 125138 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": 67930, "vin": [ { "gen": { "height": 67920 } } ], "vout": [ { "amount": 365555777167, "target": { "key": "3aa6d731b027196dd9ebafc2ae8b1af9f183bab1d7c28399911d921262b63472" } } ], "extra": [ 1, 224, 30, 46, 146, 105, 15, 7, 19, 101, 117, 218, 68, 200, 128, 253, 188, 254, 98, 189, 250, 242, 167, 98, 134, 251, 189, 233, 111, 29, 229, 136, 108, 2, 17, 0, 0, 0, 4, 2, 107, 89, 243, 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