Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aed649cb8712729f9447f197da808adbf4825309ae3dea4d43987b666febab58

Tx prefix hash: d63f9b3968dd5c9ab8e8e57d618f7766458fbca7816a8de3c10baafb735be645
Tx public key: 2a42ea1d6d444f9cbe126e7a7815d1888bf72bda3d8522b40dd184a409035165
Timestamp: 1578053318 Timestamp [UCT]: 2020-01-03 12:08:38 Age [y:d:h:m:s]: 05:102:18:20:32
Block: 37703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1223415 RingCT/type: yes/0
Extra: 012a42ea1d6d444f9cbe126e7a7815d1888bf72bda3d8522b40dd184a4090351650211000000b119e17573000000000000000000

1 output(s) for total of 460.336234317000 dcy

stealth address amount amount idx
00: a1a5cb571a0a6799dcdec82660c22bc49c0c9aa8a21c7fd95eb98975ebc6262c 460.336234317000 64100 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": 37713, "vin": [ { "gen": { "height": 37703 } } ], "vout": [ { "amount": 460336234317, "target": { "key": "a1a5cb571a0a6799dcdec82660c22bc49c0c9aa8a21c7fd95eb98975ebc6262c" } } ], "extra": [ 1, 42, 66, 234, 29, 109, 68, 79, 156, 190, 18, 110, 122, 120, 21, 209, 136, 139, 247, 43, 218, 61, 133, 34, 180, 13, 209, 132, 164, 9, 3, 81, 101, 2, 17, 0, 0, 0, 177, 25, 225, 117, 115, 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