Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecc6ea4e6718ce96d9ee4d6712df8f84404847eba8446d6da99fffb337a07e14

Tx prefix hash: 121a2934a37c261199dfba5c4d0bdc2d7f02af49738101102908065a320c24ba
Tx public key: 8afb454afce01f20725013fb6289d5f52e9f3a20cd6c1fd0f2d79c0d5f23fee4
Timestamp: 1685604327 Timestamp [UCT]: 2023-06-01 07:25:27 Age [y:d:h:m:s]: 01:224:06:15:56
Block: 772651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421694 RingCT/type: yes/0
Extra: 018afb454afce01f20725013fb6289d5f52e9f3a20cd6c1fd0f2d79c0d5f23fee4021100000005e6d27f9c000000000000000000

1 output(s) for total of 1.689999843000 dcy

stealth address amount amount idx
00: de1f7f9dbd81baeef913b0cbee61cf9cadb42daaa8bbe4abbb17bca0f661e65b 1.689999843000 1222072 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": 772661, "vin": [ { "gen": { "height": 772651 } } ], "vout": [ { "amount": 1689999843, "target": { "key": "de1f7f9dbd81baeef913b0cbee61cf9cadb42daaa8bbe4abbb17bca0f661e65b" } } ], "extra": [ 1, 138, 251, 69, 74, 252, 224, 31, 32, 114, 80, 19, 251, 98, 137, 213, 245, 46, 159, 58, 32, 205, 108, 31, 208, 242, 215, 156, 13, 95, 35, 254, 228, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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