Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0acb4d40aff44964273a72f64219c73d1c6e4c634dbc7d31edc406d1f58d2f8d

Tx prefix hash: bb2ab80e1a0cce5283096dfaf307f1c81b72d0faacafbc6501bf40ee87d896f8
Tx public key: cc73e3103d31c9dfd2474c0cadcc8af2d9c2d01a9bc1ef65b9c519487f3da8c1
Timestamp: 1718528615 Timestamp [UCT]: 2024-06-16 09:03:35 Age [y:d:h:m:s]: 00:278:15:23:28
Block: 1045377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199089 RingCT/type: yes/0
Extra: 01cc73e3103d31c9dfd2474c0cadcc8af2d9c2d01a9bc1ef65b9c519487f3da8c102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82008ee7e15c1b4bd907976ab204fb4ddf15475d97e43b84ee7fd54f9de04e8e 0.600000000000 1514930 of 15

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": 1045387, "vin": [ { "gen": { "height": 1045377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82008ee7e15c1b4bd907976ab204fb4ddf15475d97e43b84ee7fd54f9de04e8e" } } ], "extra": [ 1, 204, 115, 227, 16, 61, 49, 201, 223, 210, 71, 76, 12, 173, 204, 138, 242, 217, 194, 208, 26, 155, 193, 239, 101, 185, 197, 25, 72, 127, 61, 168, 193, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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