Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bdbf2e93e07f167f9c2f08a4482c644426afa7ecf1f9884e8cc24383d5e8b3f

Tx prefix hash: 50156099faa9205bb65dfded9125348a86364e18abe3a52bfd908b3b8295f633
Tx public key: 011d07f87e9e8ff209ec4941ea7963a83619f46f3c9d2afcbe98a89edaece673
Timestamp: 1694097083 Timestamp [UCT]: 2023-09-07 14:31:23 Age [y:d:h:m:s]: 01:223:11:02:45
Block: 842995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420813 RingCT/type: yes/0
Extra: 01011d07f87e9e8ff209ec4941ea7963a83619f46f3c9d2afcbe98a89edaece673021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.988115446000 dcy

stealth address amount amount idx
00: d07eec02c8b7598188ccb4e192863c2acca1ce10d0da6c1d75a6f9309e5cc071 0.988115446000 1296177 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": 843005, "vin": [ { "gen": { "height": 842995 } } ], "vout": [ { "amount": 988115446, "target": { "key": "d07eec02c8b7598188ccb4e192863c2acca1ce10d0da6c1d75a6f9309e5cc071" } } ], "extra": [ 1, 1, 29, 7, 248, 126, 158, 143, 242, 9, 236, 73, 65, 234, 121, 99, 168, 54, 25, 244, 111, 60, 157, 42, 252, 190, 152, 168, 158, 218, 236, 230, 115, 2, 17, 0, 0, 0, 9, 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