Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c3681244677f5c900c217e76dbda369d3a2cef2142401f47d4c115d2fad9407

Tx prefix hash: 320ef2e38e0070b9616e0343faca5fe52e9772ae232f40ad0aa0e58dfa4b6c3e
Tx public key: bab4ce71b4b609aa1eff202d7d38f8cbf61bb284f4df8ca659bfdf577702bf4c
Timestamp: 1695819311 Timestamp [UCT]: 2023-09-27 12:55:11 Age [y:d:h:m:s]: 01:188:20:04:26
Block: 857288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396008 RingCT/type: yes/0
Extra: 01bab4ce71b4b609aa1eff202d7d38f8cbf61bb284f4df8ca659bfdf577702bf4c02110000000133af99f4000000000000000000

1 output(s) for total of 0.886031220000 dcy

stealth address amount amount idx
00: 5843473bb7b05fcd5b0da06a5822c9506fe0963db91f474a841612e2e24b45c1 0.886031220000 1311402 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": 857298, "vin": [ { "gen": { "height": 857288 } } ], "vout": [ { "amount": 886031220, "target": { "key": "5843473bb7b05fcd5b0da06a5822c9506fe0963db91f474a841612e2e24b45c1" } } ], "extra": [ 1, 186, 180, 206, 113, 180, 182, 9, 170, 30, 255, 32, 45, 125, 56, 248, 203, 246, 27, 178, 132, 244, 223, 140, 166, 89, 191, 223, 87, 119, 2, 191, 76, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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