Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 858be2e5605482b6b032b2bfb08b664c2ab1c340bde8059d1ba7a93a376cc9d1

Tx prefix hash: 289dfe9bde07edc0801688750bb5d7d0d9aeb4338d330fc6b39d8a80957a25ae
Tx public key: 43d3ceb795b82ed9f7b8efdece9fef071939c1842acfd95d3e3b07ae3bc4f425
Timestamp: 1700652424 Timestamp [UCT]: 2023-11-22 11:27:04 Age [y:d:h:m:s]: 01:142:13:14:48
Block: 897157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363043 RingCT/type: yes/0
Extra: 0143d3ceb795b82ed9f7b8efdece9fef071939c1842acfd95d3e3b07ae3bc4f425021100000001faf35c9c000000000000000000

1 output(s) for total of 0.653651736000 dcy

stealth address amount amount idx
00: 751ba88c1ff17fb23da3bdb8de35be4d34e3355570839cef03a7a1f883a175e2 0.653651736000 1353522 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": 897167, "vin": [ { "gen": { "height": 897157 } } ], "vout": [ { "amount": 653651736, "target": { "key": "751ba88c1ff17fb23da3bdb8de35be4d34e3355570839cef03a7a1f883a175e2" } } ], "extra": [ 1, 67, 211, 206, 183, 149, 184, 46, 217, 247, 184, 239, 222, 206, 159, 239, 7, 25, 57, 193, 132, 42, 207, 217, 93, 62, 59, 7, 174, 59, 196, 244, 37, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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