Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d64bd6e683d3f0ec410c4da973867300a3b2ce79c0555b285944f575d0f9fdfa

Tx prefix hash: f9d486beda7dea54534ba4dd38ec9606b62a3549138e61ae96a9bf3bc5c3de79
Tx public key: 7355df77bc410d0d0b64def6ab02b82a17eb46ea37f791340666dd8f9a713014
Timestamp: 1578051226 Timestamp [UCT]: 2020-01-03 11:33:46 Age [y:d:h:m:s]: 05:006:17:10:23
Block: 37681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154963 RingCT/type: yes/0
Extra: 017355df77bc410d0d0b64def6ab02b82a17eb46ea37f791340666dd8f9a7130140211000000efed383139000000000000000000

1 output(s) for total of 460.413507005000 dcy

stealth address amount amount idx
00: bb18c8d4bd17ba447b2a1abaa3e48c595e85b0104773d2a288e42d774f652fd3 460.413507005000 64066 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": 37691, "vin": [ { "gen": { "height": 37681 } } ], "vout": [ { "amount": 460413507005, "target": { "key": "bb18c8d4bd17ba447b2a1abaa3e48c595e85b0104773d2a288e42d774f652fd3" } } ], "extra": [ 1, 115, 85, 223, 119, 188, 65, 13, 13, 11, 100, 222, 246, 171, 2, 184, 42, 23, 235, 70, 234, 55, 247, 145, 52, 6, 102, 221, 143, 154, 113, 48, 20, 2, 17, 0, 0, 0, 239, 237, 56, 49, 57, 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