Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17d417d70c3352490e139ef28e0d472426e2ed888d5314789152f14bea1786f3

Tx prefix hash: 292ecaf5d40b769c839007acc2302244c050ddc5c90cd7d532a48e0e2f9ee1b3
Tx public key: e2e96798f9e725a78de525a52b69da8ac0a8d2637857d30e69d035c63d81f5db
Timestamp: 1581946038 Timestamp [UCT]: 2020-02-17 13:27:18 Age [y:d:h:m:s]: 05:012:18:18:17
Block: 66639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1162303 RingCT/type: yes/0
Extra: 01e2e96798f9e725a78de525a52b69da8ac0a8d2637857d30e69d035c63d81f5db0211000000010aca7173000000000000000000

1 output(s) for total of 369.156415854000 dcy

stealth address amount amount idx
00: 1fd19f60dcd3e145469ef45b64b37d0af4392e0c4447292b60991ac7d849db44 369.156415854000 122782 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": 66649, "vin": [ { "gen": { "height": 66639 } } ], "vout": [ { "amount": 369156415854, "target": { "key": "1fd19f60dcd3e145469ef45b64b37d0af4392e0c4447292b60991ac7d849db44" } } ], "extra": [ 1, 226, 233, 103, 152, 249, 231, 37, 167, 141, 229, 37, 165, 43, 105, 218, 138, 192, 168, 210, 99, 120, 87, 211, 14, 105, 208, 53, 198, 61, 129, 245, 219, 2, 17, 0, 0, 0, 1, 10, 202, 113, 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